Skip to content

Conversation

@vrutkovs
Copy link
Contributor

@vrutkovs vrutkovs commented Mar 5, 2020

This PR moves all functions which create or modify Ignition in a single file and abstract Ignition config in IgnConfig.

The change would enable us to replace Ignition v2 implementation with Ignition v3 using build tags (or any other way on compile-time).

This ensures machineconfigs are created with Ignition 2.2.0 and Openstack shim is created using Ignition v2.4.0.

/cc @LorbusChris @cgwalters @openshift/installer

@openshift-ci-robot openshift-ci-robot requested review from a team, LorbusChris and cgwalters March 5, 2020 20:14
@openshift-ci-robot openshift-ci-robot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. labels Mar 5, 2020
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign smarterclayton
You can assign the PR to them by writing /assign @smarterclayton in a comment when ready.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@vrutkovs
Copy link
Contributor Author

vrutkovs commented Mar 5, 2020

/cc @smarterclayton @abhinavdahiya

@abhinavdahiya
Copy link
Contributor

this is too big a commit to review. can you break it apart into new functions and then moving existing code to it.

also ignConfig isn't a great name.
adding abstractions for dropin, unit, file etc is a little too much for when the installer should actually just move to v3 in one go and the server (here the igntion on the host) is the one that should understand both.

@vrutkovs
Copy link
Contributor Author

vrutkovs commented Mar 5, 2020

this is too big a commit to review. can you break it apart into new functions and then moving existing code to it.

Okay, will do

also ignConfig isn't a great name.

It can be addressed later.

adding abstractions for dropin, unit, file etc is a little too much for when the installer should actually just move to v3 in one go and the server (here the igntion on the host) is the one that should understand both.

That can be done in approximately 4.6 time, when RHCOS switches to Ignition v3. OKD installer would like to do that earlier.

@vrutkovs vrutkovs force-pushed the master-ign-abstraction branch from 16f9110 to c785f43 Compare March 5, 2020 20:45
@LorbusChris
Copy link
Contributor

/cc @openshift/openshift-team-mco-maintainers

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I opened a PR a month ago to support Spec 2.4 in the provider: hashicorp/terraform-provider-ignition#67

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this may not be needed after all. If you don't have to use 2.4 everywhere, I'd say let's not in order to keep changes to a mininum.

@LorbusChris
Copy link
Contributor

MCO should probably be updated to natively use Ignition Spec 2.4 before this can go in?
/cc @runcom

@LorbusChris
Copy link
Contributor

openshift/machine-config-operator#1543 adds support for Spec 2.4,
but it needs the RawExtension PR first (openshift/machine-config-operator#996)

@openshift-ci-robot openshift-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 9, 2020
@vrutkovs vrutkovs force-pushed the master-ign-abstraction branch from c785f43 to 08305f9 Compare March 10, 2020 09:08
@openshift-ci-robot openshift-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 10, 2020
@vrutkovs vrutkovs force-pushed the master-ign-abstraction branch 5 times, most recently from 0d3c284 to 3de649f Compare April 6, 2020 08:19
@vrutkovs
Copy link
Contributor Author

vrutkovs commented Apr 6, 2020

ovirt flaked, workers didn't join on openstack

/retest

@vrutkovs vrutkovs changed the title WIP Abstract Ignition operations in a single file Abstract Ignition operations in a single file Apr 6, 2020
@openshift-ci-robot openshift-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 6, 2020
@vrutkovs
Copy link
Contributor Author

vrutkovs commented Apr 6, 2020

/hold

Openstack workers don't join the cluster

@vrutkovs
Copy link
Contributor Author

Imagestream import issues
/retest

@vrutkovs
Copy link
Contributor Author

/retest

@vrutkovs
Copy link
Contributor Author

/retest

@vrutkovs
Copy link
Contributor Author

/hold cancel

All issues resolved, PTAL

@openshift-ci-robot openshift-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 26, 2020
@vrutkovs vrutkovs force-pushed the master-ign-abstraction branch from 60fa219 to f4fb1b6 Compare May 29, 2020 22:17
@stbenjam
Copy link
Member

/test e2e-metal-ipi

1 similar comment
@stbenjam
Copy link
Member

/test e2e-metal-ipi

@vrutkovs vrutkovs force-pushed the master-ign-abstraction branch from f4fb1b6 to c5ede55 Compare June 8, 2020 07:52
@vrutkovs
Copy link
Contributor Author

vrutkovs commented Jun 8, 2020

/retest

@vrutkovs vrutkovs force-pushed the master-ign-abstraction branch from c5ede55 to f9e7abd Compare June 9, 2020 11:36
@vrutkovs vrutkovs force-pushed the master-ign-abstraction branch from f9e7abd to 4fc5d48 Compare July 1, 2020 09:12
@LorbusChris
Copy link
Contributor

@vrutkovs do you mind updating this PR once again? Spec 3 support has now merged into MCO, the migration could happen be done any time now.
I propose we collect all ignition-related functions in one file as proposed in this PR (however we won't be needing the build flag), and then flip the switch to v3 in a follow up PR.

@vrutkovs
Copy link
Contributor Author

vrutkovs commented Jul 6, 2020

I propose we collect all ignition-related functions in one file as proposed in this PR (however we won't be needing the build flag), and then flip the switch to v3 in a follow up PR

We still need RHCOS to run Ign3 for tests to pass

@vrutkovs vrutkovs force-pushed the master-ign-abstraction branch from 4fc5d48 to e333587 Compare July 6, 2020 09:50
@LorbusChris
Copy link
Contributor

/retest

@openshift-ci-robot
Copy link
Contributor

@vrutkovs: The following tests failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/prow/e2e-aws-scaleup-rhel7 e333587 link /test e2e-aws-scaleup-rhel7
ci/prow/e2e-ovirt e333587 link /test e2e-ovirt
ci/prow/e2e-openstack e333587 link /test e2e-openstack
ci/prow/e2e-aws e333587 link /test e2e-aws
ci/prow/verify-codegen e333587 link /test verify-codegen

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@vrutkovs
Copy link
Contributor Author

Superceded by #3871

@vrutkovs vrutkovs closed this Jul 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants